v8.18.0

Compare Source

🚀 Features

• eslint-plugin: [switch-exhaustiveness-check] add support for "no default" comment (#​10218)
• eslint-plugin: [no-deprecated] report on super call of deprecated constructor (#​10397)

🩹 Fixes

• eslint-plugin: [use-unknown-in-catch-callback-variable] only flag function literals (#​10436)
• eslint-plugin: [no-base-to-string] handle more robustly when multiple toString() declarations are present for a type (#​10432)
• eslint-plugin: [no-deprecated] check if a JSX attribute is deprecated (#​10374)
• typescript peer dependency (#​10373)

❤️ Thank You

• Kim Sang Du @​developer-bandi
• Kirk Waiblinger @​kirkwaiblinger
• mdm317
• rtritto

You can read about our versioning strategy and releases on our website.

v8.18.0

Compare Source

🩹 Fixes

• typescript peer dependency (#​10373)

❤️ Thank You

• rtritto

You can read about our versioning strategy and releases on our website.

v3.7.0

Compare Source

Minor Changes

• #​326 93ea130 Thanks @​SukkaW! - This version has implemented the eslint-plugin-import-x's v3 resolver interface. This allows you to use import/require to reference eslint-import-resolver-typescript directly in your ESLint flat config:

  Previously

  // eslint.config.js
  module.exports = {
    settings: {
      'import-x/resolver': {
        typescript: {
          alwaysTryTypes: true,
        },
        // or
        require.resolve('eslint-import-resolver-typescript'):
          alwaysTryTypes: true,
        }
      }
    }
  }

  Now

  // eslint.config.js
  const {
    createTypeScriptImportResolver,
  } = require('eslint-import-resolver-typescript')
  
  module.exports = {
    settings: {
      'import-x/resolver-next': [
        createTypeScriptImportResolver({
          alwaysTryTypes: true,
        }),
      ],
    },
  }

  Note that this only works with eslint-plugin-import-x@>=4.5.0. You can't use createTypeScriptImportResolver with the older versions of eslint-plugin-import-x or any existing versions of eslint-plugin-import.

v15.2.11

Compare Source

Patch Changes

• #​1484 bcfe309 Thanks @​wormsik! - Escape paths containing spaces when using the "shell" option.

• #​1487 7dd8caa Thanks @​iiroj! - Do not treat submodule root paths as "staged files". This caused lint-staged to fail to a Git error when only updating the revision of a submodule.

v3.4.2

Compare Source

diff

Treat U+30A0 & U+30FB in Katakana Block as CJK (#​16796 by @​tats-u)

Prettier doesn't treat U+30A0 & U+30FB as Japanese. U+30FB is commonly used in Japanese to represent the delimitation of first and last names of non-Japanese people or “and”. The following “C言語・C++・Go・Rust” means “C language & C++ & Go & Rust” in Japanese.

<!-- Input (--prose-wrap=never) -->

C言
語
・
C++
・
Go
・
Rust

<!-- Prettier 3.4.1 -->
C言語・ C++ ・ Go ・ Rust

<!-- Prettier 3.4.2 -->
C言語・C++・Go・Rust

U+30A0 can be used as the replacement of the - in non-Japanese names (e.g. “Saint-Saëns” (Charles Camille Saint-Saëns) can be represented as “サン゠サーンス” in Japanese), but substituted by ASCII hyphen (U+002D) or U+FF1D (full width hyphen) in many cases (e.g. “サン=サーンス” or “サン＝サーンス”).

Fix comments print on class methods with decorators (#​16891 by @​fisker)

// Input
class A {
  @​decorator
  /** 
   * The method description
   *
  */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.1
class A {
  @​decorator
  async /**
   * The method description
   *
   */
  method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

// Prettier 3.4.2
class A {
  @​decorator
  /**
   * The method description
   *
   */
  async method(foo: Foo, bar: Bar) {
    console.log(foo);
  }
}

Fix non-idempotent formatting (#​16899 by @​seiyab)

This bug fix is not language-specific. You may see similar change in any languages. This fixes regression in 3.4.0 so change caused by it should yield same formatting as 3.3.3.

// Input
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.1 (first)
<div>
  foo
  <span>
    longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo
  </span>, abc
</div>;

// Prettier 3.4.1 (second)
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

// Prettier 3.4.2
<div>
  foo
  <span>longlonglonglonglonglonglonglonglonglonglonglonglonglonglongl foo</span>
  , abc
</div>;

v3.4.16

Compare Source

Fixed

• Ensure the TypeScript types for PluginsConfig allow undefined values (#​14668)

Changed

• Bumped lilconfig to v3.x (#​15289)